Discovery/script path fixes for stress test release pipeline#1901
Merged
Discovery/script path fixes for stress test release pipeline#1901
Conversation
weshaggard
reviewed
Aug 13, 2021
dc4c884 to
a0fb535
Compare
a0fb535 to
3bdc388
Compare
Collaborator
|
The following pipelines have been queued for testing: |
This was referenced Aug 13, 2021
weshaggard
approved these changes
Aug 13, 2021
|
Hello @azure-sdk! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Member
Author
|
/check-enforcer override |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sdkpath so we discover stress tests in the language repositoriesdeploy-stress-tests.ps1script fromeng/commonin the language repository, so that we can skip checking out the tools repo AND so we can run the pipeline targeting custom branches (otherwise the branch needs to exist in the tools repo as well).